home *** CD-ROM | disk | FTP | other *** search
- wpasupplicant in debian
- =======================
-
- wpasupplicant is now integrated into ifupdown. You can configure it in
- /etc/network/interfaces, in a similar method to configuring WEP keys[1].
- After that, wpa_supplicant will be controlled by ifupdown without further
- user intervention.
-
- For details about integration into the interfaces file, refer to
- /usr/share/doc/wpasupplicant/README.modes.gz
-
- The old method of wpa_supplicant invocation was the other way round,
- invoking it from an init script. This method is no longer recommended, however
- there are instructions below for reverting to the old behaviour.
-
- [1] As described in /usr/share/doc/wireless-tools/README.Debian
-
-
- wpasupplicant, Wireless Extension 18 and the Linux 2.6.14 kernel
- ================================================================
-
- WPA/WPA2 support was added in Wireless Extension 18.
-
- This version (or more correctly, WE 19) was included in the Linux 2.6.14
- kernel, and is therefore supported by 2.6.14-compliant drivers such as
- ipw2200 v1.0.8.
-
- wpasupplicant supports this new capability from 0.4.6.
-
- In order to take advantage of this WE 18 support you need to use
- wpasupplicant's wext driver. You may have previously used a specific driver
- such as "-D ipw" for older kernels, but to use the new WE 18 features in
- kernel 2.6.14 or later, you'll want to use the generic "wext" driver instead.
-
- You may check which version of Wireless Extensions your current kernel uses by
- inspecting /proc/net/wireless (the "WE" entry).
-
-
- wpasupplicant, Prism54 support
- ==============================
-
- Note that previously this software was compiled with support for
- driver_prism54. However, this support never worked, and is still not
- supported upstream. Therefore, I've disabled this so people do not
- get the false impression that it is actually working.
-
-
- -- Kyle McMartin <kyle@debian.org>
- Sat Jan 28 14:12:20 EST 2006
-
-
- wpa_supplicant as system daemon
- ===============================
-
- The current wpasupplicant package is not starting as system daemon per default
- anymore. We consider the old behavior as deprecated and do not support that any
- longer. You need to read this section only if you want to keep the old
- behaviour from the wpasupplicant package in Debian 3.1 (sarge).
-
- The current behavior uses wpasupplicant the other way round: ifupdown now
- controls wpasupplicant. This means the supplicant is running as long as you want
- to use the interface (i.e. it is ifupped from the ifupdown POV). For a roaming
- solution, please read the wpa_action(8) manual page.
-
- Please note that past packages didn't provide any roaming solution by itself.
- The fact that it was a system daemon enabled the user to make it 'control'
- ifupdown, so that mechanisms like guessnet can choose the current location. If
- you insist on this behavior, please install the init script yourself.
-
- We do however, provide a somewhat improved init script in the
- /usr/share/doc/wpasupplicant/examples/ directory of the package. Follow the
- instructions below to revert to the deprecated behaviour:
-
- Copy the file into the /etc/init.d directory and make it executable:
-
- cp /usr/share/doc/wpasupplicant/examples/wpa_supplicant.init-daemon \
- /etc/init.d/wparoamd
- chmod +x /etc/init.d/wparoamd
-
- The init daemon must be altered to suit your persnal configuration. Edit the
- script so that INTERFACE, CONFIG and DRIVER are defined, then make sure the
- init daemon begins with the following commands:
-
- update-rc.d wparoamd start 15 2 3 4 5 . stop 90 0 1 6 .
- invoke-rc.d wparoamd start
-
- The following commands revert the above changes:
-
- invoke-rc.d wparoamd stop
- update-rc.d wparoamd remove
- rm -f /etc/init.d/wparoamd
-
- A howto for using a system daemon for these purposes is located at:
-
- http://www.debian-administration.org/articles/312
-